Event rate assessment

ABSTRACT

This document discusses, among other things, systems and methods to determine an alert state for a patient using received physiologic information, determine an event rate for the alert state, and adjust determination of a composite risk for the patient using the determined event rate.

CLAIM OF PRIORITY

This application is a continuation of U.S. Application Serial No. 15/961,209, filed Apr. 24, 2018, which claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Pat. Application Serial Number 62/492,172, filed on Apr. 29, 2017, which are herein incorporated by reference in their entireties.

TECHNICAL FIELD

This document relates generally to medical devices, and more particularly, but not by way of limitation, to systems, devices, and methods for event rate assessment of congestive heart failure.

BACKGROUND

Congestive heart failure (CHF) can be described as a reduction in ability of the heart to deliver enough blood to meet bodily needs, affecting over five million people in the United States alone. CHF patients commonly have enlarged heart with weakened cardiac muscles, resulting in reduced contractility and poor cardiac output of blood.

CHF is typically a chronic condition, but can also occur suddenly, affecting the left, right, or both sides of a heart. If CHF affects the left ventricle, signals that control the left ventricular contraction can be delayed, causing left ventricular dysfunction, further decreasing the pumping efficiency of the heart.

SUMMARY

This document discusses, among other things, systems and methods to determine an alert state for a patient using received physiologic information, determine an event rate for the alert state, and adjust a determination of a composite risk for the patient using the determined event rate.

An example (e.g., “Example 1”) of subject matter (e.g., a medical device) may include a signal receiver circuit configured to receive physiologic information for a plurality of patients; a risk assessment circuit configured to: determine an alert state for each patient using the received physiologic information and a threshold; determine an event rate for the plurality of patients for a specific alert state; and adjust a composite HF risk determination for the plurality of patients using the determined event rate.

In Example 2, the subject matter of Example 1 may optionally be configured such that, to adjust the composite HF risk determination for the plurality of patients, the risk assessment circuit is configured to adjust the threshold using the determined event rate for the specific alert state.

In Example 3, the subject matter any one or more of Examples 1-2 may optionally be configured such that, to adjust the composite HF risk determination for the plurality of patients, the risk assessment circuit is configured to adjust a weighting of a signal metric used to determine the composite HF risk.

In Example 4, the subject matter any one or more of Examples 1-3 may optionally be configured such that the risk assessment circuit is configured to adjust the composite HF risk determination to optimize the determined event rate for the specific alert state.

In Example 5, the subject matter any one or more of Examples 1-4 may optionally be configured such that the alert state includes an IN alert state and an OUT alert state, and the risk assessment circuit may optionally be configured to determine event rates for the plurality of patients for each alert state, and to adjust the composite HF risk determination using the determined event rates.

In Example 6, the subject matter any one or more of Examples 1-5 may optionally be configured such that the risk assessment circuit is configured to determine an event rate ratio using the determined event rates for the IN alert state and OUT alert state, and, to adjust the composite HF risk determination using the determined event rates, the risk assessment circuit may optionally be configured to adjust the composite HF risk determination using the determined event rate ratio.

In Example 7, the subject matter any one or more of Examples 1-6 may optionally be configured such that, to adjust the composite HF risk determination, the risk assessment circuit is configured to adjust the threshold to maximize the event rate ratio, where the event rate ratio is the event rate for the IN alert state divided by the event rate for the OUT alert state.

In Example 8, the subject matter any one or more of Examples 1-7 may optionally be configured such that the risk assessment circuit is configured to determine the event rate using a number of heart failure events in each alert state, wherein the heart failure events include an intervention associated with a congestive heart failure (CHF) condition.

In Example 9, the subject matter any one or more of Examples 1-8 may optionally be configured such that the risk assessment circuit is configured to determine the alert state for each patient using a comparison of the determined composite HF risk to the threshold.

An example (e.g., “Example 10”) of subject matter (e.g., a machine-readable medium) may include instructions that, when performed by a medical device, cause the medical device to: receive physiologic information for a plurality of patients; determine an alert state for each patient using the received physiologic information and a threshold; determine an event rate for the plurality of patients for a specific alert state; and adjust a composite HF risk determination for the plurality of patients using the determined event rate.

In Example 11, the subject matter of Example 10 may optionally be configured such that the instructions that, when performed by the medical device, cause the medical device to adjust the composite HF risk determination include instructions to adjust the threshold using the determined event rate for the specific alert state.

In Example 12, the subject matter of any one or more of Examples 10-11 may optionally be configured such that the instructions that, when performed by the medical device, cause the medical device to adjust the composite HF risk determination include instructions to adjust a weighting of a signal metric used to determine the composite HF risk.

In Example 13, the subject matter of any one or more of Examples 10-12 may optionally be configured to include instructions that, when performed by the medical device, cause the medical device to adjust the composite HF risk determination to optimize the determined event rate for the specific alert state.

In Example 14, the subject matter of any one or more of Examples 10-13 may optionally be configured such that the alert state includes an IN alert state and an OUT alert state, and optionally be configured to include instructions that, when performed by the medical device, cause the medical device to: determine event rates for the plurality of patients for each of the IN and OUT alert states; and adjust the composite HF risk determination using the determined event rates.

In Example 15, the subject matter of any one or more of Examples 10-14 may optionally be configured to include instructions that, when performed by the medical device, cause the medical device to: determine an event rate ratio using the determined event rates for the IN alert state and OUT alert state, and adjust the composite HF risk determination using the determined event rate ratio.

An example (e.g., “Example 16”) of subject matter (e.g., a method) may include receiving physiologic information for a plurality of patients using a signal receiver circuit; determining, using a risk assessment circuit, an alert state for each patient using the received physiologic information and a threshold; determining, using the risk assessment circuit, an event rate for the plurality of patients for a specific alert state; and adjusting, using the risk assessment circuit, a composite HF risk determination for the plurality of patients using the determined event rate.

In Example 17, the subject matter of Example 16 may optionally be configured such that the adjusting the composite HF risk determination includes adjusting the threshold using the determined event rate for the specific alert state.

In Example 18, the subject matter of any one or more of Examples 16-17 may optionally be configured such that the adjusting the composite HF risk determination includes adjusting a weighting of a signal metric used to determine the composite HF risk.

In Example 19, the subject matter of any one or more of Examples 16-18 may optionally be configured such that the alert state includes an IN alert state and an OUT alert state, wherein the determining the event rate includes determine event rates for the plurality of patients for each alert state, and wherein the adjusting the composite HF risk determination includes using the determined event rates.

In Example 20, the subject matter of any one or more of Examples 16-19 may optionally be configured to include: determining an event rate ratio using the determined event rates for the IN alert state and OUT alert state, wherein the adjusting the composite HF risk determination using the determined event rates includes adjusting the composite HF risk determination using the determined event rate ratio.

An example (e.g., “Example 21”) of subject matter (e.g., a system or apparatus) may optionally combine any portion or combination of any portion of any one or more of Examples 1-20 to include “means for” performing any portion of any one or more of the functions or methods of Examples 1-20, or a “non-transitory machine-readable medium” including instructions that, when performed by a machine, cause the machine to perform any portion of any one or more of the functions or methods of Examples 1-20.

This summary is intended to provide an overview of subject matter of the present patent application. It is not intended to provide an exclusive or exhaustive explanation of the disclosure. The detailed description is included to provide further information about the present patent application. Other aspects of the disclosure will be apparent to persons skilled in the art upon reading and understanding the following detailed description and viewing the drawings that form a part thereof, each of which are not to be taken in a limiting sense.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

FIG. 1 illustrates an example patient status of a patient suffering from congestive heart failure (CHF) over time.

FIG. 2 illustrates an example congestive heart failure (CHF) index over time and one or more thresholds.

FIG. 3 illustrates an example system including a signal receiver circuit and a risk assessment circuit.

FIG. 4 illustrates an example system including an ambulatory medical device (AMD) configured to sense or detect information from a patient.

FIG. 5 illustrates an example system including an ambulatory medical device (AMD) coupled to an external or remote system.

FIG. 6 illustrates an example of a Cardiac Rhythm Management (CRM) system.

FIGS. 7A-7B illustrate example event rate ratios (ERRs) for congestive heart failure (CHF) metrics.

FIGS. 8A-8B illustrate example event rates (ERs) per patient year for congestive heart failure (CHF) metrics.

FIG. 9A illustrates example event rates (ERs) per patient year for multiple patient risk groups across a range of programmable thresholds.

FIG. 9B illustrates example event rate ratios (ERRs) between the high risk and low risk groups across a range of programmable thresholds.

FIG. 10 illustrates a block diagram of an example machine upon which any one or more of the techniques discussed herein may perform.

DETAILED DESCRIPTION

Ambulatory medical devices, including implantable, leadless, or wearable medical devices configured to monitor, detect, or treat various cardiac conditions resulting in a reduced ability of a heart to sufficiently deliver blood to a body, such as congestive heart failure (CHF). Various ambulatory medical devices can be implanted in a patient’s body or otherwise positioned on or about the patient to monitor patient physiologic information, such as heart sounds, respiration (e.g., respiration rate, tidal volume, etc.), impedance (e.g., thoracic impedance), pressure, cardiac activity (e.g., heart rate), physical activity, or one or more other physiological parameters of a patient, or to provide electrical stimulation or one or more other therapies or treatments to optimize or control contractions of the heart.

Traditional cardiac rhythm management (CRM) devices, such as pacemakers, defibrillators, or cardiac monitors, include subcutaneous devices implanted in a chest of a patient, having one or more leads to position one or more electrodes or other sensors at various locations in the heart, such as in one or more of the atria or ventricles. Separate from, or in addition to, the one or more electrodes or other sensors of the leads, the CRM device can include one or more electrodes or other sensors (e.g., a pressure sensor, an accelerometer, a gyroscope, a microphone, etc.) powered by a power source in the CRM device. The one or more electrodes or other sensors of the leads, the CRM device, or a combination thereof, can be configured detect physiologic information from, or provide one or more therapies or stimulation to, the patient.

Leadless cardiac pacemakers (LCP) include small (e.g., smaller than traditional implantable CRM devices), self-contained devices configured to detect physiologic information from or provide one or more therapies or stimulation to the heart without traditional lead or implantable CRM device complications (e.g., required incision and pocket, complications associated with lead placement, breakage, or migration, etc.). In certain examples, an LCP can have more limited power and processing capabilities than a traditional CRM device; however, multiple LCP devices can be implanted in the heart to detect physiologic information from, or provide one or more therapies or stimulation to, one or more chambers of the heart. The multiple LCP devices can communicate between themselves, or one or more other implanted or external devices.

In contrast, wearable or external medical sensors or devices can be configured to detect or monitor physiologic information of the patient without required implant or an in-patient procedure for placement, battery replacement, or repair. However, such sensors and devices, in contrast to implantable, subcutaneous, or leadless medical devices, can suffer from reduced patient compliance, increased detection noise, or reduced detection sensitivity.

Risk stratification for CHF often requires some initial assessment time to establish a baseline level or condition from one or more sensors or physiologic information which to detect deviation from and determine a risk of a heart failure event (HFE), or from which to predict or stratify the risk of the patient experiencing an HFE in a following period. Changes in physiologic information can be aggregated and weighted based on one or more patient-specific stratifiers. However, such changes and risk stratification are often associated with one or more thresholds, for example, having a clinical sensitivity and specificity across a target population with respect to a specific condition (e.g., CHF), etc., and one or more specific time periods, such as daily values, short term averages (e.g., daily values aggregated over a number of days), long term averages (e.g., daily values aggregated over a number of short term periods or a greater number of days (sometimes different days than used for the short term average)), etc.

The present inventors have recognized, among other things, that thresholds, parameters, or sensor weightings used to determine a risk of worsening congestive heart failure (CHF) in a patient or across a patient population can be optimized using a count or ratio of heart failure events (HFE) occurring in inside (IN) or outside (OUT) of an alert state, improving the sensitivity and specificity of existing sensors in predicting or assessing CHF, and diverting existing resources to patients in more immediate need of intervention.

Physiologic information from a patient can be evaluated to identify a patient alert state, such as alert states associated with a specified risk of CHF, a level associated with one or more signal metrics generated using at least a portion of the patient physiologic information, etc. Alert states can include inside (IN) an alert state, outside (OUT) an alert state, or one or more other intermediate or other alert states. One or more heart failure events (HFEs) can be determined using the patient physiologic information, or using information about a patient admission or hospitalization, or a treatment or intervention associated with a congestive heart failure condition. HFE rates can be calculated in the one or more alert states. Further, one or more event rate ratios (ERRs) can be calculated as a ratio of event rates in one or more different alert states. For example, an event rate ratio (ERR) can be calculated as a ratio of event rates during IN versus OUT alert states.

FIG. 1 illustrates an example patient status 100 of a patient suffering from congestive heart failure (CHF) over time. The dashed line represents a decline in patient CHF status, with the individual dips representing heart failure events (HFEs) occurring as the patient status declines. In other examples, the overall status can incline or decline in the presence of more or less HFEs. In an example, HFEs can be include patient admissions or unscheduled visits into a hospital or clinic for heart failure treatment. In other examples, HFEs can include sudden, acute changes in patient physiologic information or status. In an example, an HFE can be detected, or the severity of an HFE can be determined, using one or more detected biomarkers, such as a natriuretic peptide, a B-type natriuretic peptide (BNP), an N-terminal proBNP (NT-proBNP), etc.

FIG. 2 illustrates an example congestive heart failure (CHF) index over time and one or more thresholds. The CHF index can be indicative of the patient CHF status. In FIG. 1 , a decrease in patient status indicated worsening CHF. In this example, an increase in the CHF index indicates a worsening CHF status, or an increased risk of a worsening CHF status or impending CHF event. In this example, when the CHF index is below a threshold, the patient can be determined to be in an OUT alert state; when the CHF index is above a threshold, the patient can be determined to be in an IN alert state.

The thresholds in FIG. 2 include an OUT threshold (THRESHOLD_(OUT)) in the OUT alert state, and an IN threshold (THRESHOLD_(IN)) in the IN alert state. The IN threshold can be different than the OUT threshold to provide hysteresis to avoid sudden state changes. In other examples, one or more other or additional thresholds or states can be provided (e.g., an Intermediate alert state, etc.).

In an example, the CHF index and thresholds can include an index, score, or other metric or measure that indicates a CHF condition of a patient, such as described in one or more of the commonly assigned: Qi An et al., U.S. Application Serial No. 14/510,392, titled “Methods and apparatus for detecting heart failure decompensation event and stratifying the risk of the same”; Robert. J. Sweeney et al., U.S. Application Serial No. 14/282,353, titled “Methods and apparatus for stratifying risk of heart failure decompensation”; Qi An et al. U.S. Application No. 13/726,786, titled “Risk stratification based heart failure detection algorithm”, each of which is incorporated herein by reference in their entirety.

In an example, an event rate (ER) can be determined for each alert state by counting individual heart failure events (HFEs) in each alert state. For example, an ER for the OUT alert state (ER_(OUT)) or the IN alert state (ER_(IN)) can be determined as the number of HFEs in the specific alert state, over the time the patient is in the alert state (e.g., number of days in the specific alert state, etc.), such as illustrated in equations (1) and (2):

$ER_{OUT} = \frac{\# Events\mspace{6mu} while\mspace{6mu} OUT\mspace{6mu} alert\mspace{6mu} state}{\# Days\mspace{6mu} OUT\mspace{6mu} alert\mspace{6mu} state}$

$ER_{IN} = \frac{\# Events\mspace{6mu} while\mspace{6mu} IN\mspace{6mu} alert\mspace{6mu} state}{\# Days\mspace{6mu} IN\mspace{6mu} alert\mspace{6mu} state}$

In an example, one or more event rate ratios (ERRs) can be determined using a ratio of the event rates across one or more alert states, such as illustrated in equation (3):

$ERR = \frac{ER_{IN}}{ER_{OUT}}$

FIG. 3 illustrates an example system (e.g., a medical device, etc.) 300 including a signal receiver circuit 302 and a risk assessment circuit 304. The signal receiver circuit 302 can be configured to receive patient information, such as physiologic information of a patient or group of patients. The risk assessment circuit 304 can be configured to determine an alert state of a patient using the received physiologic information, to determine an event rate for the patient or the group of patients for each alert state, and to adjust a composite worsening heart failure (HF) risk calculation for the patient or group of patients using the determined event rates. In certain examples, the signal receiver circuit 302 can be configured to receive a count of heart failure events (HFEs) for a patient or a group of patients from a user, a clinician, medical records, etc. In other examples, the system 300 can receive an indication of an intervention associated with congestive heart failure (CHF), and store a count of individual HFEs associated with the patient or the group of patients. In an example, risk assessment circuit 304 can determine the event rate for the patient or the group of patients for each alert state using the received HFEs.

The worsening HF risk calculation can include a composite CHF risk indicator determined using a combination of physiological data that change in response to cardiac decompensation, including one or more of a first heart sound, a third heart sound, respiration rate, respiration volume, thoracic impedance, heart rate, or daily patient activity. In certain examples, the individual sensor inputs can be stratified, or one or more sensor weightings can be adjusted depending on the values of one or more other physiologic parameters. In other examples, the physiologic data can include one or more biomarkers detected from the patient.

In an example, the risk assessment circuit 304 can be configured to adjust one or more thresholds (e.g., CHF thresholds, etc.), or individual sensor or parameter weightings to optimize one or more of an event rate or event rate ratio. For example, a heart failure threshold or parameter can be adjusted to minimize an OUT alert state event rate (ER_(OUT)), to minimize an IN alert state event rate (ER_(IN)), or to maximize or minimize an event rate ratio (e.g., maximize ERR_(IN)/ERR_(OUT), etc.).

In other examples, the risk assessment circuit 304 can be configured to provide an output to a user, such as to a display or one or more other user interface, the output including event rate or event rate ratio information, or a recommendation to a user to adjust a threshold or sensor weighting to optimize one or more of an event rate or event rate ratio, or to provide a desired outcome (e.g., limit a number of OUT alert heart failure events (HFEs) to a specified number or rate, etc.). In other examples, the event rate or event rate ratio information can be provided to a user in addition to other threshold or patient physiologic information.

In certain examples, the signal receiver circuit 302 can be configured to receive information from a plurality of patients, and the risk assessment circuit 304 can be configured to determine high risk patients from the plurality of patients using determined event rates or event rate ratios for the plurality of patients. For example, the risk assessment circuit 304 can be configured to adjust a weighting of one or more sensors in a composite CHF risk indicator indicative of a risk of worsening heart failure to optimize an event rate or an event rate ratio of a specific patient or a group of patients, such as to help identify those patients in the group having the highest risk of worsening heart failure, or to determine a risk of worsening heart failure of a specific patient.

FIG. 4 illustrates an example system 400 including an ambulatory medical device (AMD) 410 configured to sense or detect information from a patient 401. In an example, the AMD 410 can include an implantable medical device (IMD), a subcutaneous or leadless medical device, a wearable or external medical device, or one or more other implantable or external medical devices or patient monitors. The AMD 410 can include a single device, or a plurality of medical devices or monitors configured to detect patient information.

The AMD 410 can include a respiration sensor 402 configured to receive respiration information (e.g., a respiration rate (RR), a respiration volume (tidal volume), etc.) of the patient 401, a heart sound sensor 404 configured to receive heart sound information of the patient 401, a thoracic impedance sensor 406 configured to receive impedance information from the patient 401, a cardiac sensor 408 configured to receive cardiac electrical information from the patient 401, and an activity sensor 408 configured to receive information about a physical motion (e.g., activity, posture, etc.) of the patient 401, or one or more other sensors configured to receive physiologic information of the patient 401.

In an example, the sensors in the AMD 410 include existing physiologic sensors. However, using the system and methods described herein, the sensitivity and specificity of one or more metrics associated with a risk of worsening congestive heart failure (CHF) detected using existing sensors can be increased without otherwise increasing system cost or power, or negatively affecting usable battery life of the existing sensors.

FIG. 5 illustrates an example system 500 including an ambulatory medical device (AMD) 502 coupled to an external or remote system 504, such as an external programmer. In an example, the AMD 502 can be an implantable device, an external device, or a combination or permutation of one or more implantable or external devices. In an example, one or more of the signal receiver circuit 302 or the risk assessment circuit 304 can be located in the AMD 502, or the remote system 504. The remote system 504 can include a specialized device configured to interact with the AMD 502, including to program or receive information from the AMD 502.

FIG. 6 illustrates an example of a Cardiac Rhythm Management (CRM) system 600 and portions of an environment in which the CRM system 600 can operate. The CRM system 600 can include an ambulatory medical device, such as an implantable medical device (IMD) 610 that can be electrically coupled to a heart 605 such as through one or more leads 608A-C coupled to the IMD 610 using a header 611, and an external system 620 that can communicate with the IMD 610 such as via a communication link 603. The IMD 610 may include an implantable cardiac device such as a pacemaker, an implantable cardioverter-defibrillator (ICD), or a cardiac resynchronization therapy defibrillator (CRT-D). The IMD 610 can include one or more monitoring or therapeutic devices such as a subcutaneously implanted device, a wearable external device, a neural stimulator, a drug delivery device, a biological therapy device, or one or more other ambulatory medical devices. The IMD 610 may be coupled to, or may be substituted by a monitoring medical device such as a bedside or other external monitor.

As illustrated in FIG. 6 , the IMD 610 can include a hermetically sealed can 612 that can house an electronic circuit that can sense a physiological signal in the heart 605 and can deliver one or more therapeutic electrical pulses to a target region, such as in the heart, such as through one or more leads 608A-C. In certain examples, the CRM system 600 can include only a single lead, such as 608B, or can include only two leads, such as 608A and 608B.

The lead 608A can include a proximal end that can be configured to be connected to IMD 610 and a distal end that can be configured to be placed at a target location such as in the right atrium (RA) 631 of the heart 605. The lead 608A can have a first pacing-sensing electrode 641 that can be located at or near its distal end, and a second pacing-sensing electrode 642 that can be located at or near the electrode 641. The electrodes 641 and 642 can be electrically connected to the IMD 610 such as via separate conductors in the lead 608A, such as to allow for sensing of the right atrial activity and optional delivery of atrial pacing pulses. The lead 608B can be a defibrillation lead that can include a proximal end that can be connected to IMD 610 and a distal end that can be placed at a target location such as in the right ventricle (RV) 632 of heart 605. The lead 608B can have a first pacing-sensing electrode 652 that can be located at distal end, a second pacing-sensing electrode 653 that can be located near the electrode 652, a first defibrillation coil electrode 654 that can be located near the electrode 653, and a second defibrillation coil electrode 655 that can be located at a distance from the distal end such as for superior vena cava (SVC) placement. The electrodes 652 through 655 can be electrically connected to the IMD 610 such as via separate conductors in the lead 608B. The electrodes 652 and 653 can allow for sensing of a ventricular electrogram and can optionally allow delivery of one or more ventricular pacing pulses, and electrodes 654 and 655 can allow for delivery of one or more ventricular cardioversion/defibrillation pulses. In an example, the lead 608B can include only three electrodes 652, 654, and 655. The electrodes 652 and 654 can be used for sensing or delivery of one or more ventricular pacing pulses, and the electrodes 654 and 655 can be used for delivery of one or more ventricular cardioversion or defibrillation pulses. The lead 608C can include a proximal end that can be connected to the IMD 610 and a distal end that can be configured to be placed at a target location such as in a left ventricle (LV) 634 of the heart 605. The lead 608C may be implanted through the coronary sinus 633 and may be placed in a coronary vein over the LV such as to allow for delivery of one or more pacing pulses to the LV. The lead 608C can include an electrode 661 that can be located at a distal end of the lead 608C and another electrode 662 that can be located near the electrode 661. The electrodes 661 and 662 can be electrically connected to the IMD 610 such as via separate conductors in the lead 608C such as to allow for sensing of the LV electrogram and optionally allow delivery of one or more resynchronization pacing pulses from the LV.

The IMD 610 can include an electronic circuit that can sense a physiological signal. The physiological signal can include an electrogram or a signal representing mechanical function of the heart 605. The hermetically sealed can 612 may function as an electrode such as for sensing or pulse delivery. For example, an electrode from one or more of the leads 608A-C may be used together with the can 612 such as for unipolar sensing of an electrogram or for delivering one or more pacing pulses. A defibrillation electrode from the lead 608B may be used together with the can 612 such as for delivering one or more cardioversion/defibrillation pulses. In an example, the IMD 610 can sense impedance such as between electrodes located on one or more of the leads 608A-C or the can 612. The IMD 610 can be configured to inject current between a pair of electrodes, sense the resultant voltage between the same or different pair of electrodes, and determine impedance using Ohm’s Law. The impedance can be sensed in a bipolar configuration in which the same pair of electrodes can be used for injecting current and sensing voltage, a tripolar configuration in which the pair of electrodes for current injection and the pair of electrodes for voltage sensing can share a common electrode, or tetrapolar configuration in which the electrodes used for current injection can be distinct from the electrodes used for voltage sensing. In an example, the IMD 610 can be configured to inject current between an electrode on the RV lead 608B and the can 612, and to sense the resultant voltage between the same electrodes or between a different electrode on the RV lead 608B and the can 612. A physiologic signal can be sensed from one or more physiological sensors that can be integrated within the IMD 610. The IMD 610 can also be configured to sense a physiological signal from one or more external physiologic sensors or one or more external electrodes that can be coupled to the IMD 610. Examples of the physiological signal can include one or more of heart rate, heart rate variability, intrathoracic impedance, intracardiac impedance, arterial pressure, pulmonary artery pressure, RV pressure, LV coronary pressure, coronary blood temperature, blood oxygen saturation, one or more heart sounds, physical activity or exertion level, physiologic response to activity, posture, respiration, body weight, or body temperature.

The arrangement and functions of these leads and electrodes are described above by way of example and not by way of limitation. Depending on the need of the patient and the capability of the implantable device, other arrangements and uses of these leads and electrodes are.

The CRM system 600 can include a patient chronic condition-based HF risk assessment circuit, such as illustrated in the commonly assigned Qi An et al., U.S. Application Serial No. 14/510,392, titled “Methods and apparatus for detecting heart failure decompensation event and stratifying the risk of the same,” incorporated herein by reference in its entirety. The patient chronic condition-based HF risk assessment circuit can include a signal analyzer circuit and a risk stratification circuit. The signal analyzer circuit can receive patient chronic condition indicators and one or more physiologic signals from the patient, and select one or more patient-specific sensor signals or signal metrics from the physiologic signals. The signal analyzer circuit can receive the physiologic signals from the patient using the electrodes on one or more of the leads 608A-C, or physiologic sensors deployed on or within the patient and communicated with the IMD 610. The risk stratification circuit can generate a composite risk index indicative of the probability of the patient later developing an event of worsening of HF (e.g., an HF decompensation event) such as using the selected patient-specific sensor signals or signal metrics. The HF decompensation event can include one or more early precursors of an HF decompensation episode, or an event indicative of HF progression such as recovery or worsening of HF status.

The external system 620 can allow for programming of the IMD 610 and can receives information about one or more signals acquired by IMD 610, such as can be received via a communication link 603. The external system 620 can include a local external IMD programmer. The external system 620 can include a remote patient management system that can monitor patient status or adjust one or more therapies such as from a remote location.

The communication link 603 can include one or more of an inductive telemetry link, a radio-frequency telemetry link, or a telecommunication link, such as an internet connection. The communication link 603 can provide for data transmission between the IMD 610 and the external system 620. The transmitted data can include, for example, real-time physiological data acquired by the IMD 610, physiological data acquired by and stored in the IMD 610, therapy history data or data indicating IMD operational status stored in the IMD 610, one or more programming instructions to the IMD 610 such as to configure the IMD 610 to perform one or more actions that can include physiological data acquisition such as using programmably specifiable sensing electrodes and configuration, device self-diagnostic test, or delivery of one or more therapies.

The patient chronic condition-based HF risk assessment circuit may be implemented at the external system 620, which can be configured to perform HF risk stratification such as using data extracted from the IMD 610 or data stored in a memory within the external system 620. Portions of patient chronic condition-based HF risk assessment circuit may be distributed between the IMD 610 and the external system 620.

Portions of the IMD 610 or the external system 620 can be implemented using hardware, software, or any combination of hardware and software. Portions of the IMD 610 or the external system 620 may be implemented using an application-specific circuit that can be constructed or configured to perform one or more particular functions, or can be implemented using a general-purpose circuit that can be programmed or otherwise configured to perform one or more particular functions. Such a general-purpose circuit can include a microprocessor or a portion thereof, a microcontroller or a portion thereof, or a programmable logic circuit, or a portion thereof. For example, a “comparator” can include, among other things, an electronic circuit comparator that can be constructed to perform the specific function of a comparison between two signals or the comparator can be implemented as a portion of a general-purpose circuit that can be driven by a code instructing a portion of the general-purpose circuit to perform a comparison between the two signals. While described with reference to the IMD 610, the CRM system 600 could include a subcutaneous medical device (e.g., subcutaneous ICD, subcutaneous diagnostic device), wearable medical devices (e.g., patch based sensing device), or other external medical devices.

FIGS. 7A-7B illustrate example event rate ratios (ERRs) for two congestive heart failure (CHF) metrics. FIG. 7A illustrates example ERRs (ERR_(IN)/ERR_(OUT)) across a range of programmable HeartLogic thresholds. The HeartLogic risk indicator is a composite CHF risk indicator determined using a combination of physiological data that change in response to cardiac decompensation: heart sounds (including S1 and S3), respiration rate and volume, thoracic impedance, heart rate and daily patient activity.

FIG. 7B illustrates example ERRs (High/Low) across a range of N-terminal pro B-type natriuretic peptide (NT-proBNP) thresholds. NT-pro-BNP is a biomarker indicative of adverse outcome in heart failure patients. Event rates for the NT-proBNP metric were calculated as HIGH if the HFE was associated with a biomarker concentration at or over the defined threshold, and LOW if the HFE was associated with a biomarker concentration below the defined threshold.

FIGS. 8A-8B illustrate example event rates (ERs) per patient year for two congestive heart failure (CHF) metrics. FIG. 8A illustrates example ERs for patients IN alert state and separately for patients OUT alert state across a range of programmable HeartLogic thresholds. FIG. 8B illustrates example ERs across a range of NT-proBNP thresholds.

FIG. 9A illustrates example event rates (ERs) per patient year for multiple patient risk groups across a range of programmable HeartLogic thresholds. The multiple patient risk groups include high risk, intermediate risk, and low risk patient groups. High risk patient groups include those having a HeartLogic level above the threshold. Intermediate risk patient groups include those having a HeartLogic level between the threshold and a small value (e.g., 2). Low risk patient groups include those having a HeartLogic level lower than the small value (e.g., 2). Significant resources are directed to the low risk patient group, (e.g., 41%) that can be directed elsewhere.

FIG. 9B illustrates example event rate ratios (ERRs) between the high risk and low risk groups of FIG. 9A across a range of programmable HeartLogic thresholds. As illustrated, the ER for the high risk groups range from 12 to 31 times higher than the low risk groups.

The HeartLogic CHF risk indicator, across any threshold between 10 and 40, has a higher likelihood of predicting a heart failure event (HFE) than other biomarkers or clinical variables.

TABLE 1 Multivariate Analysis of Predictors of Event Rates Clinical Variable Event Rate Ratio (95% CI) p-value HeartLogic ≥ 10 5.06 (3.17, 8.08) <0.0001 HeartLogic ≥ 12 5.20 (3.26, 8.30) <0.0001 HeartLogic ≥ 14 5.48 (3.40, 8.84) <0.0001 HeartLogic ≥ 16 5.91 (3.63, 9.62) <0.0001 HeartLogic ≥ 18 6.51 (3.98, 10.65) <0.0001 HeartLogic ≥ 20 6.35 (4.10, 9.85) <0.0001 HeartLogic ≥ 22 7.00 (4.49, 10.92) <0.0001 HeartLogic ≥ 24 6.80 (4.39, 10.52) <0.0001 HeartLogic ≥ 26 7.44 (4.69, 11.80) <0.0001 HeartLogic ≥ 28 7.53 (4.68, 12.11) <0.0001 HeartLogic ≥ 30 6.27 (3.88, 10.15) <0.0001 HeartLogic ≥ 32 6.25 (3.91, 9.99) <0.0001 HeartLogic ≥ 34 5.71 (3.74, 8.73) <0.0001 HeartLogic ≥ 36 4.77 (3.14, 7.25) <0.0001 HeartLogic ≥ 38 4.72 (3.03, 7.34) <0.0001 HeartLogic ≥ 40 4.18 (2.71, 6.43) <0.0001 NT Pro-BNP ≥ 1000 pg/mL 2.40 (1.29, 4.46)* 0.0055* History of AF or AF1 2.34 (1.32, 4.14)* 0.0036* History of renal disease 2.30 (1.40, 3.79)* 0.0010* NYHA III or IV 2.17 (1.21, 3.88)* 0.0094* Total plasma protein ≥ 7.1 1.78 (1.03, 3.08)* 0.0377* Sodium ≥ 140 1.33 (0.80, 2.21)* 0.2747* LVEF ≥ 28 1.11 (0.69, 1.79)* 0.6751 * Diabetes 1.11 (0.67, 1.83)* 0.6871 *

In other examples, other variables can include, separately or in combination with one or more of the variables in Table 1, above, one or more of: age, gender, body mass index (BMI), blood pressure (BP) (e.g., systolic, diastolic, etc.), total hemoglobin, prior myocardial infarction (MI), K+ level, NA+ level, creatine, blood urea nitrogen (BUN), etc.

Event Rae Ratio (ERR) and p-values for clinical variables* were calculated at HeartLogic threshold of 16.

The robustness of the HeartLogic indicator is further evidenced across a range of NT-proBNP thresholds.

TABLE 2 Robustness of HeartLogic versus NT-proBNP Across Thresholds NT-proBNP Cut-off HL Threshold 500 600 700 800 900 1000 1100 1200 1300 1400 1500 10 0.0138 0.0108 0.0108 0.0020 0.0015 0.0018 0.0017 0.0023 0.0025 0.0015 0.0006 12 0.0184 0.0146 0.0146 0.0030 0.0023 0.0027 0.0025 0.0032 0.0034 0.0021 0.0008 14 0.0170 0.0132 0.0129 0.0026 0.0019 0.0024 0.0022 0.0028 0.0029 0.0018 0.0007 16 0.0126 0.0097 0.0095 0.0019 0.0014 0.0018 0.0017 0.0021 0.0022 0.0013 0.0004 18 0.0095 0.0072 0.0071 0.0014 0.0012 0.0014 0.0014 0.0017 0.0018 0.0010 0.0003 20 0.0059 0.0042 0.0040 0.0007 0.0005 0.0007 0.0007 0.0009 0.0009 0.0005 0.0002 22 0.0055 0.0040 0.0039 0.0007 0.0006 0.0007 0.0007 0.0009 0.0009 0.0006 0.0002 24 0.0085 0.0061 0.0064 0.0014 0.0013 0.0017 0.0017 0.0021 0.0023 0.0016 0.0007 26 0.0097 0.0073 0.0080 0.0020 0.0020 0.0025 0.0025 0.0032 0.0035 0.0025 0.0012 28 0.0086 0.0067 0.0081 0.0024 0.0023 0.0031 0.0033 0.0044 0.0051 0.0036 0.0016 30 0.0081 0.0065 0.0083 0.0023 0.0036 0.0050 0.0054 0.0072 0.0082 0.0063 0.0030 32 0.0126 0.0109 0.0145 0.0048 0.0046 0.0068 0.0077 0.0103 0.0122 0.0090 0.0044 34 0.0124 0.0108 0.0146 0.0046 0.0045 0.0066 0.0075 0.0102 0.0122 0.0097 0.0048 36 0.0224 0.0205 0.0282 0.0101 0.0103 0.0149 0.0174 0.0232 0.0272 0.0212 0.0122 38 0.0256 0.0239 0.0323 0.0140 0.0147 0.0205 0.0241 0.0310 0.0358 0.0294 0.0204 40 0.0471 0.0456 0.0630 0.0296 0.0316 0.0442 0.0516 0.0666 0.0769 0.0639 0.0456

In other examples, HeartLogic and B-type natriuretic peptide (BNP) (or other biomarker) detection or alerts can be combined, increasing effectiveness of HF detection, or HF risk determination. For example, the event rate of patients having a HeartLogic score at or above a threshold (e.g., 16, etc.) and a biomarker (e.g., NT-proBNP) level at or above a threshold (e.g., NT-proBNP greater than or equal to 1000, etc.), is significantly higher than using the biomarker or the HeartLogic threshold alone. For example, using a biomarker alone, detected event rates (events per patient-year) below or greater than or equal to a threshold (e.g., NT-proBNP of 1000) were 0.11 and 0.42, respectively. Using HeartLogic alone, detected event rates below or greater than or equal to a threshold (e.g., Heartlogic of 16) were 0.08 and 0.8, respectively. However, combining the biomarker and HeartLogic detections, detected event rates for a HeartLogic score below a threshold (e.g., 16) and a biomarker below or greater than or equal to a threshold (e.g., NT-proBNP of 1000) were 0.02 and 0.16, respectively, and detected event rates for the HeartLogic score greater than or equal to the threshold (e.g., 16) and the biomarker below or greater than or equal to the threshold (e.g., NT-proBNP of 1000) were 0.47 and 1.00, respectively. The combination of biomarkers, and specifically BNP (e.g., NT-proBNP) and HeartLogic significantly augments the ability to identify patients having elevated risk of an HFE, in contrast to existing systems using HeartLogic or biomarkers alone. Such detection provides significant advantages for existing systems, improving the sensitivity and specificity of existing sensors in predicting or assessing CHF, and diverting existing resources to patients in more immediate need of intervention.

FIG. 10 illustrates a block diagram of an example machine 1000 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. Portions of this description may apply to the computing framework of one or more of the medical devices described herein, such as the IMD, the external programmer, etc.

Examples, as described herein, may include, or may operate by, logic or a number of components, or mechanisms in the machine 1000. Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the machine 1000 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, in an example, the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuitry. For example, under operation, execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the machine 1000 follow.

In alternative embodiments, the machine 1000 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 1000 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 1000 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

The machine (e.g., computer system) 1000 may include a hardware processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1004, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) 1006, and mass storage 1008 (e.g., hard drive, tape drive, flash storage, or other block devices) some or all of which may communicate with each other via an interlink (e.g., bus) 1030. The machine 1000 may further include a display unit 1010, an alphanumeric input device 1012 (e.g., a keyboard), and a user interface (UI) navigation device 1014 (e.g., a mouse). In an example, the display unit 1010, input device 1012, and UI navigation device 1014 may be a touch screen display. The machine 1000 may additionally include a signal generation device 1018 (e.g., a speaker), a network interface device 1020, and one or more sensors 1016, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 1000 may include an output controller 1028, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

Registers of the processor 1002, the main memory 1004, the static memory 1006, or the mass storage 1008 may be, or include, a machine-readable medium 1022 on which is stored one or more sets of data structures or instructions 1024 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1024 may also reside, completely or at least partially, within any of registers of the processor 1002, the main memory 1004, the static memory 1006, or the mass storage 1008 during execution thereof by the machine 1000. In an example, one or any combination of the hardware processor 1002, the main memory 1004, the static memory 1006, or the mass storage 1008 may constitute the machine-readable medium 1022. While the machine-readable medium 1022 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 1024.

The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1000 and that cause the machine 1000 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon based signals, sound signals, etc.). In an example, a non-transitory machine-readable medium comprises a machine-readable medium with a plurality of particles having invariant (e.g., rest) mass, and thus are compositions of matter. Accordingly, non-transitory machine-readable media are machine-readable media that do not include transitory propagating signals. Specific examples of non-transitory machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 1024 may be further transmitted or received over a communications network 1026 using a transmission medium via the network interface device 1020 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 1020 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1026. In an example, the network interface device 1020 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 1000, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software. A transmission medium is a machine-readable medium.

Various embodiments are illustrated in the figures above. One or more features from one or more of these embodiments may be combined to form other embodiments. Method examples described herein can be machine or computer-implemented at least in part. Some examples may include a computer-readable medium or machine-readable medium encoded with instructions operable to configure an electronic device or system to perform methods as described in the above examples. An implementation of such methods can include code, such as microcode, assembly language code, a higher-level language code, or the like. Such code can include computer readable instructions for performing various methods. The code can form portions of computer program products. Further, the code can be tangibly stored on one or more volatile or non-volatile computer-readable media during execution or at other times.

The above detailed description is intended to be illustrative, and not restrictive. The scope of the disclosure should, therefore, be determined with references to the appended claims, along with the full scope of equivalents to which such claims are entitled. 

What is claimed is:
 1. A system, comprising: a signal receiver circuit configured to receive physiologic information of a patient; a risk stratification circuit configured to determine a composite risk for the patient using a combination of signal metrics, the composite risk indicative of a risk of the patient to develop a heart failure (HF) decompensation event; and a risk assessment circuit configured to: determine an alert state for the patient using the received physiologic information; receive an indication of an occurrence of a HF event for the patient; determine a HF event rate for the alert state, the HF event rate representing a count of HF events for the alert state per unit time; and adjust the determination of the composite risk for the patient using the determined HF event rate to increase a sensitivity or a specificity of the physiologic information in assessing the risk of the patient to develop the HF decompensation event.
 2. The system of claim 1, wherein the indication of the occurrence of the HF event for the patient includes an indication of HF treatment to the patient.
 3. The system of claim 2, wherein the indication of HF treatment to the patient includes an admission or unscheduled visit into a hospital or clinic for HF treatment or an indication that the patient received HF treatment.
 4. The system of claim 1, wherein to adjust the determination of the composite risk for the patient includes to adjust the combination of signal metrics or a weighting of a signal metric of the combination of signal metrics used to determine the composite risk.
 5. The system of claim 1, wherein the alert state comprises an IN alert state, wherein the risk assessment circuit is configured to adjust the determination of the composite risk for the patient to minimize the occurrence of the IN alert state.
 6. The system of claim 1, wherein the received physiologic information includes a sensor input, wherein to adjust the determination of the composite risk for the patient includes to adjust the sensor input or a weighting of the sensor input using the determined HF event rate for the alert state.
 7. The system of claim 1, wherein the received physiologic information comprises the signal metrics.
 8. The system of claim 1, wherein the risk stratification circuit is configured to determine the signal metrics using the received physiological information.
 9. A method, comprising: receiving physiologic information of a patients using a signal receiver circuit; determining, using a risk stratification circuit, a composite risk for the patient using a combination of signal metrics, the composite risk indicative of a risk of the patient to develop a heart failure (HF) decompensation event; determining, using a risk assessment circuit, an alert state for the patient using the received physiologic information; receiving, using the risk assessment circuit, an indication of an occurrence of a HF event for the patient; determining, using the risk assessment circuit, a HF event rate for the alert state, the HF event rate representing a count of HF events for the alert state per unit time; and adjusting, using the risk assessment circuit, the determination of the composite risk for the patient using the determined HF event rate to increase a sensitivity or a specificity of the physiologic information in assessing the risk of the patient to develop the HF decompensation event.
 10. The method of claim 9, wherein the indication of the occurrence of the HF event for the patient includes an indication of HF treatment to the patient.
 11. The method of claim 10, wherein the indication of HF treatment to the patient includes an admission or unscheduled visit into a hospital or clinic for HF treatment or an indication that the patient received HF treatment.
 12. The method of claim 9, wherein adjusting the determination of the composite risk for the patient includes adjusting the combination of signal metrics or a weighting of a signal metric of the combination of signal metrics used to determine the composite risk.
 13. The method of claim 9, wherein the alert state comprises an IN alert state. wherein adjusting the determination of the composite risk for the patient includes to minimize the occurrence of the IN alert state.
 14. The method of claim 9, wherein the received physiologic information includes a sensor input, wherein adjusting the determination of the composite risk for the patient includes adjusting the sensor input or a weighting of the sensor input using the determined HF event rate for the alert state.
 15. The system of claim 1, wherein the received physiologic information comprises the signal metrics.
 16. The system of claim 1, comprising determining, using the risk stratification circuit, the signal metrics using the received physiological information.
 17. A system, comprising: a signal receiver circuit configured to receive physiologic information of a patient; a risk stratification circuit configured to determine signal metrics of the patient using the received physiologic information and to determine a composite risk of worsening status for the patient using a combination of the determined signal metrics; and a risk assessment circuit configured to: determine an alert state for the patient using the received physiologic information; receive an indication of an occurrence of an adverse medical event for the patient; determine an event rate for the alert state, the event rate representing a count of events for the alert state per unit time; and adjust the determination of the composite risk for the patient using the determined event rate to increase a sensitivity or a specificity of the physiologic information in assessing the risk of worsening status for the patient to experience the adverse medical event.
 18. The system of claim 17, wherein the indication of the occurrence of the adverse medical event includes information about an unscheduled patient admission or hospitalization or a treatment or intervention associated with the worsening status for the patient.
 19. The system of claim 17, wherein the composite risk of worsening status for the patient includes a composite risk indicative of a risk of the patient do develop a HF decompensation event, wherein the indication of the occurrence of the adverse medical event for the patient comprises an indication of an occurrence of a HF event for the patient, wherein the event rate comprises a HF event rate representative of a count of HF events for the alert state per unit time.
 20. The system of claim 17, wherein the received physiologic information includes a sensor input, wherein to adjust the determination of the composite risk for the patient includes to adjust the sensor input or a weighting of the sensor input using the determined event rate for the alert state. 